-
Notifications
You must be signed in to change notification settings - Fork 606
Updated the comparison logic to handle sequences separately #12251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12251
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (1 Unrelated Failure)As of commit 321bc98 with merge base 264ac90 ( BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D77893628 |
@pytorchbot label "release notes: none" |
8a33c41
to
bf60729
Compare
…12251) Summary: Previously, the numerical comparators were designed to compare two inputs regardless of whether they were sequences, which involved stacking a list of tensors into one for comparison. The updated logic now restricts comparators to only compare two tensors at a time, with sequence handling managed externally. Differential Revision: D77893628
This pull request was exported from Phabricator. Differential Revision: D77893628 |
bf60729
to
be68445
Compare
…12251) Summary: Previously, the numerical comparators were designed to compare two inputs regardless of whether they were sequences, which involved stacking a list of tensors into one for comparison. The updated logic now restricts comparators to only compare two tensors at a time, with sequence handling managed externally. Reviewed By: Gasoonjia Differential Revision: D77893628
…12251) Summary: Previously, the numerical comparators were designed to compare two inputs regardless of whether they were sequences, which involved stacking a list of tensors into one for comparison. The updated logic now restricts comparators to only compare two tensors at a time, with sequence handling managed externally. Reviewed By: Gasoonjia Differential Revision: D77893628
be68445
to
263dd38
Compare
This pull request was exported from Phabricator. Differential Revision: D77893628 |
…12251) Summary: Pull Request resolved: pytorch#12251 Previously, the numerical comparators were designed to compare two inputs regardless of whether they were sequences, which involved stacking a list of tensors into one for comparison. The updated logic now restricts comparators to only compare two tensors at a time, with sequence handling managed externally. Reviewed By: Gasoonjia Differential Revision: D77893628
This pull request was exported from Phabricator. Differential Revision: D77893628 |
263dd38
to
321bc98
Compare
Summary: Previously, the numerical comparators were designed to compare two inputs regardless of whether they were sequences, which involved stacking a list of tensors into one for comparison. The updated logic now restricts comparators to only compare two tensors at a time, with sequence handling managed externally.
Differential Revision: D77893628